home *** CD-ROM | disk | FTP | other *** search
- Path: mail2news.demon.co.uk!genesis.demon.co.uk
- From: Lawrence Kirby <fred@genesis.demon.co.uk>
- Newsgroups: comp.lang.c
- Subject: Re: heap fragmentation
- Date: Thu, 29 Feb 96 13:53:24 GMT
- Organization: none
- Message-ID: <825602004snz@genesis.demon.co.uk>
- References: <remigy.37.001137F2@uni-duesseldorf.de>
- Reply-To: fred@genesis.demon.co.uk
- X-NNTP-Posting-Host: genesis.demon.co.uk
- X-Newsreader: Demon Internet Simple News v1.27
- X-Mail2News-Path: genesis.demon.co.uk
-
- In article <remigy.37.001137F2@uni-duesseldorf.de>
- remigy@uni-duesseldorf.de "Mathias Remigy" writes:
-
- >Hi,
- >
- >I have written a program that dynamically allocates
- >matrices, defined as _double **M_, taking care to free
- >them after use.
- >
- >The functions have been tested, and, as far as I can tell
- >as a C novice, they are bug free.
- >
- >The problem is that the program crashes every once in a while,
- >complaining about allocation problem.
-
- You need to be more specific. If the program is exiting cleanly after
- encountering an allocation failure (e.g. malloc returning a null pointer)
- that is one thing, heap corruption is quite another.
-
- >Could heap fragmentation
- >be the snag, and if it is, what can I do about it ?
-
- What sort of system are you running on? Is it possible that you are simply
- running out of memory?
-
- --
- -----------------------------------------
- Lawrence Kirby | fred@genesis.demon.co.uk
- Wilts, England | 70734.126@compuserve.com
- -----------------------------------------
-